Smart watch extended system

ABSTRACT

A method and apparatus to provide an extended band is described. The method includes pairing a watch and a host device. The method further includes monitoring a user&#39;s status with a plurality of sensors on the host device and/or the watch, and using the extended band to do one or more of: provide alerts to the user, based on the sensor data, control the extended band from one of the devices, and share data with third parties using the extended band.

RELATED APPLICATIONS

The present application claims priority to U.S. patent application Ser.No. 14/255,923, filed on Apr. 17, 2014, which claims priority to U.S.Provisional Application No. 61/814,178, filed on Apr. 19, 2013, both ofwhich are incorporated herein by reference.

FIELD

The present invention relates to a smart watch, and more particularly toa smart watch extended system.

BACKGROUND

As accelerometers and other sensors are becoming more accurate, lowerpower, more cost-effective and smaller. There are numerous systemsavailable, which enable a user to monitor his or her activity or sleep.

For example, there are pedometers or other activity monitors that tracka user's activities to improve health. There are also some sleepmonitors, which use accelerometers.

BRIEF DESCRIPTION OF THE FIGURES

The present invention is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings and in whichlike reference numerals refer to similar elements and in which:

FIG. 1A is a block diagram of one embodiment of a system in which thepresent invention may be implemented.

FIG. 1B-1C are images of an exemplary smart watches, which may be usedthe smart watch extended system.

FIG. 2 is a block diagram of one embodiment of the extended band,including a smart watch and a mobile device working together.

FIG. 3A is an overview flowchart of one embodiment of using the extendedband.

FIG. 3B is an overview flowchart of another embodiment of using theextended band.

FIG. 4 is a flowchart of one embodiment of pairing the mobile device andthe smart watch.

FIG. 5 is a flowchart of one embodiment of selecting a connection methodbetween the mobile device and the band.

FIG. 6 is a flowchart of one embodiment of handling lost connections inthe extended band.

FIG. 7 is a flowchart of one embodiment of using the extended band.

FIG. 8 is a flowchart of one embodiment of shared processing on theextended band.

FIG. 9 is a table of some exemplary inputs and outputs using theextended band.

FIG. 10 is a flowchart of one embodiment of showing data on the smartwatch using the horological display.

FIG. 11 is a flowchart of one embodiment of resetting the hands on thewatch, in accordance with the present system.

FIG. 12 is a block diagram of one embodiment of a computer system thatmay be part of the present invention.

DETAILED DESCRIPTION

The present invention is a smart watch extended system, also referred toas an extended band system, which is a combination of a smart watchincluding sensors and a computing device. The smart watch is designed tobe worn by a user throughout the day and the night, in one embodiment.In one embodiment, the extended band system may include additionalbody-worn devices, or additional watches paired with the same computingdevice. In one embodiment, at least one sensor is worn or touched,placed next to on a soft surface, or carried by the user throughout theday. This enables the extended band to monitor the user's motions andother characteristics during the day and night. The tracking of sleepusing actigraphy enables the detection of sleep phases and circadianrhythms. In one embodiment, the data obtained by the extended band maybe used to track the user's activity level, create correlations betweenbehaviors, and/or track various other health-related features, such asergonomics, eating patterns, etc. The extended band provides usefulfeedback on the user's own status, and in one embodiment the status ofothers.

The system in the smart watch uses smart power management, andcommunication methods to enable the use of a smart watch 24 hours a day,without recharging the device for an extended period, such as a year ormore. In one embodiment, a watch battery lasts over one year, for normalusage.

The extended band provides a MACS (Monitor, Alert, Control and Share)system. The system uses sensors on the band and/or the host device toMonitor the user's state. The system can provide Alerts on one or morecomponent on the system, smart sleep cycle alarms, inactivitynotifications, etc. The system also provides Control, enabling the userto control the band from the host device and vice-versa. The system alsoenables a user to Share data about themselves with others, throughsocial media or directly with other users of the extended band system.

The smart watch includes one or more sensors, processors, andinput/output elements. In one embodiment, the output of the smart watchuses mechanical movement with dials and hands, similar to a traditionalwatch, to display data to the user. In one embodiment, the output of thesmart watch includes light emitting diodes (LEDs), in addition to dialsand hands. This type of horological system provides a high fashion andhigh function system.

The computing device may be a mobile device such as a smart phone, ortablet computer, or desktop computer. The computing device may includeone or more sensors, processors, and input/output elements. Forsimplicity, the computing device will be referred to as a host device inthis Specification. Thus, the term “host device” should be interpretedas any computing device that can establish a sporadic or continuousconnection with the smart watch.

The smart watch and host device, in one embodiment, maintain theirconnection most of the time that the devices are in range, therebyforming the extended band, consisting of the smart watch(es) and relatedhost device(s). In another embodiment, the smart watch periodicallysends its data to the host device. In another embodiment, the smartwatch sends the data to the host device upon request by the user.

The extended band is able to use the combination of sensors to get moreaccurate data, and to leverage the rich user interface of the hostdevice (speakers, large screen, vibrations, etc.). This enables theextended band, and the system as a whole, to optionally use the hostdevice for real-time feedback to the user. Furthermore, sensors in thehost device may add additional data to the system. Additionally, bycontrolling the band from the host device, the user interface provides alot more opportunities, and the user has more fine-grained control. Onthe other side, by controlling the host device from the band, the systemprovides always-in-hand control for the host device.

For example, in one embodiment the smart watch can notify the hostdevice that it is time to wake-up the user, then an application on thehost device can play sounds to wake-up the user. These sounds can gentlyfade-up and be user selectable. In one embodiment, the smart watch maywake the user directly, using a vibration.

If the host device is connected to a home automation system, it can turnon lights, raise shades, start the coffee maker, etc. Because the hostdevice is designed to be regularly charged, it can be much lesspower-conscious than a band designed to be worn for a longer time beforerecharging.

In this system, in one embodiment, the smart watch and the host devicebecome essentially extensions of each other, and all features of thehost device can be used for real-time monitoring, alert, control, andsharing. Similar, the smart watch may be used to provide monitoring,alerts, control, and sharing. For example if the host device is out ofrange (e.g. left behind), or, if the host device is a smartphone, when acall is received, the smart watch can control the host device, orprovide an alert to the user. In one embodiment, the smart watch may beused selectively for indicating a received call, e.g. when the phone isset to silent or the user is in a loud environment. In one embodiment,elements of the band's user interface and state can be controlled fromthe host device. For example, the smart watch can be put into sleepstate from the host device. Thus, the host device becomes an extensionof the smart watch and the smart watch an extension of the host device.In one embodiment, elements of the host device's user interface andstate can be controlled by the smart watch, in turn. In one embodiment,the smart watch may be used to turn on the host's ringer, turn on andoff sensors, or otherwise control the host device.

The following detailed description of embodiments of the invention makereference to the accompanying drawings in which like references indicatesimilar elements, showing by way of illustration specific embodiments ofpracticing the invention. Description of these embodiments is insufficient detail to enable those skilled in the art to practice theinvention. One skilled in the art understands that other embodiments maybe utilized and that logical, mechanical, electrical, functional, andother changes may be made without departing from the scope of thepresent invention. The following detailed description is, therefore, notto be taken in a limiting sense, and the scope of the present inventionis defined only by the appended claims.

FIG. 1A is a block diagram of one embodiment of a system in which thepresent invention may be implemented. The system includes a smart watch110 and an associated host device 115. The smart watch 110 and hostdevice 115 make up an extended band 120. Although only one smart watch110 and host device 115 are shown as being associated as an extendedband 120, in one embodiment, one or more smart watches or otherbody-worn devices may be paired with one or more host devices to form asingle extended band. For example, the user may have a smart for dailywear, and an armband for sleeping. The host device 115 may be the user'ssmart phone, as well as the user's tablet, laptop, music player, and/orother device. Thus, in one embodiment, a smart watch may be paired tomultiple hosts, and a host may be paired to multiple smart watches orother body-worn devices, in one embodiment. In one embodiment, if thereare a plurality of host devices, the host devices communicate with eachother. In one embodiment, the smart watches are host-agnostic, and ableto pair with a variety of devices with a variety of operating systemsand applications. In one embodiment, when there are multiple availablebody-worn devices, the system determines which one is being worn by theuser, and utilizes data only from that one. The determination may bemade based on movement data, temperature data or other information fromthe body-worn device. In one embodiment, the user may also add theinformation. In one embodiment, the system may be capable of having morethan one active body-worn device at the same time. For example, a usermay wear the smart watch, and also a separate bracelet band. In oneembodiment, the system combines data from the sensors of the multipledevices in such an instance.

The extended band 120 may be coupled via a low bandwidth directconnection such as Bluetooth 4.0 or similar connection mechanism. In oneembodiment, the connection between the smart watch 110 and host device115 may be continuous, periodic, or sporadic. In one embodiment, thepreferred connection is continuous, enabling the use of the host device115 as the input and output for the smart watch 110, and enablingfine-grained control of the watch. The host device 115 may be coupled toa network 150, such as the Internet. In one embodiment, the smart watch110 may be coupled to the network 150, such as the Internet. In oneembodiment, the connection between a smart watch 110 and host device 115may be through a network 150. This configuration still forms an extendedband 120.

The extended band 120 may be coupled through the network 150 to a server160. The server 160 may be a remote server or a local device that actsas a server. The server 160 may be used to collect data from multipleusers/devices. In one embodiment, the network 150 may also enable use ofthird party data 180, or provision of data to third parties 185. In oneembodiment, the network connection may also enable the extended band 120to connect to an emergency destination 170.

In one embodiment, data from the extended band 120 may be shared withvarious third party recipients 185. The third party recipients 185 inone embodiment may include social networks, such as FACEBOOK®, TWITTER®,GOOGLE+®, PINTREST® or other social networks, blogs, websites set up forthe purpose, such as a competition site set up by NIKE® or anotherextended band supporter, or other third party recipients 185.

In one embodiment, an extended band 120 may also share data with anotheruser's extended band through network 150, without going through server160 or third parties 185. In another embodiment, data may be sharedthrough server 160 and/or third party recipients 185. For example, oneuser's post on TWITTER® or check-in on FOURSQUARE® may be received byanother user's extended band 120, and shared with the user through theuser interface provided by host device 115. As another example, theextended bands of both people may provide their data to a server 160,associated with supporting the extended bands. The server 160 may sharethe extended band data with other users, who are associated with theowner of the extended band. This association may be voluntary (e.g.,friends or connections set up by the user), circumstantial (e.g., userscompeting in the same competition, or being matched for an event),locational (e.g. users participating in the same race, or being inproximity), or otherwise established. In one embodiment, the bands mayshare data directly, without using the server 185 as the intermediary,if the users are associated.

FIG. 1B illustrates an exemplary appearance of a smart watch, in oneembodiment of the present invention. The smart watch 110 includes asubdial to provide information to the user about the data obtained bythe sensors. In one embodiment, the dial may be the same dial that showsthe date, as illustrated in this figure. In one embodiment, the dateindicator also becomes the sleep state indicator, here shown by a smallmoon at the top of the inner ring of numbers. The same dial and handthat shows the date during daytime hours is used to indicate sleep statefor the monitoring, at night. In one embodiment, the user manually setsthe sleep state indicator. In one embodiment the user inputs data to thesmart watch using the crown push button. The outer ring of numbersreflects the step goal/sleep goal percentage, in one embodiment. Duringthe day, the percentage of the step goals reached is shown (as can beseen the display is between 0 and 100%). At night, the percentage of thesleep goal reached is shown, again between 0 and 100%. In oneembodiment, instead of a goal percentage, the actual step count may bedisplayed on a dial.

FIG. 1C illustrates another configuration of a watch face. Here, thereare separate subdials for the state indicator 197, the step count/steppercent or sleep count/sleep percent 199, and the date indicator 198.The date indicator 198 in this example is shown as a dial, where only asmall portion is visible through a window. This type of displaymechanism is known in the art, and may be used for the date, state, orother aspect of the display. In this example, the state indicator 197shows one of three states: sleep state (moon), normal activitymonitoring state (sun), and activity counting (walking man). Theactivity counting state is used when the user is exercising, in oneembodiment, to measure exercise intensity and provide exercise coaching.Other configurations may also be used.

FIG. 2 is a block diagram of one embodiment of the extended band,including a smart watch 210 and a host device 260 working together.Although only one smart watch 210 or band is shown, and one host device260 is shown, it should be understood that multiple devices 210 may worktogether in various ways. In the below example, each logic is reproducedin both the smart watch 210 and the host device 260. In one embodiment,certain logics may be implemented in only one of the devices. If a logicor element exists in both devices, in one embodiment, the processingshared between the devices, and both devices can contribute data andprocessing power.

The smart watch 210 includes a plurality of sensors 215. The sensors, inone embodiment, may involve sensors used to detect the user'sphysiological condition. Such sensors may include an accelerometer,gyroscope, thermometer (potentially two thermometers, one for ambientand one for body temperature), barometer, etc. In one embodiment,additional sensors focused on medical applications may also be included.Such sensors may include blood glucose sensors, blood pressure sensors,blood oxygenation sensors, and other sensors. In one embodiment, thesensors may be coupled to the smart watch 210 or host device 260wirelessly or using a wired connection.

The sensor data, obtained by sensors 215, is passed to band sensor dataprocessing 220. In one embodiment, the sensor data processing 220 isimplemented using a processor. In one embodiment, the sensors 215 may becoupled to a separate lower powered processor, and store the sensor datatemporarily in a buffer (not shown). In one embodiment, the higherpowered processor, which implements sensor data processing 220, may beturned on as needed. In one embodiment, the sensor data processing 220may also be a low power processor, and any processing requiring higherpower may use the host device 260. The host sensor data processing 270may provide additional processing power.

Power control system 240 controls the processors and sensors of thesmart watch device. In one embodiment, the smart watch 210 is powered bya watch battery 254, which is not rechargeable. The power control system240 manages the sensor testing frequency, processing, and communicationwith host device 260 to reduce power consumption, and enable an extendedbattery life. In one embodiment, under normal use conditions, the watchbattery 254 is designed to last up to two years, without replacement. Inanother embodiment, the watch battery 254 may be rechargeable using aplug-in or proximity charging technique. In one embodiment, by shiftingout put from LEDs (light emitting diodes) to dials and hands controlledvia micromotors, controlled by micromotor controller 256, the powerconsumption for the display is reduced.

One disadvantage of a micromotor controlled hand arrangement is thatjarring can cause the hand to be misaligned compared to the actual time.In one embodiment, the smart watch 210 includes a movement tracker 217which tracks the movements of the hands that are used to indicate thetime. The tracker 217 tracks each motion of the hands, to enablecomparison of the movement against the actual change in time. Thisenables the system to accurately adjust the hands of a horologicalclock, if they get misaligned due to accidental motion, jarring, oranother reason

Hand reset logic 218 is used to reset the hands to the proper locationif they are jarred. As noted, the movement tracker 217 tracks themovement of the hands. Clock logic 232 obtains current accurate clockdata, in one embodiment from host device 260. If the host device is asmart phone, the smart phone has a real-time clock source that isaccurate in GPS or network clock data. This information is obtained byclock logic 232, and used to assist in correctly resetting the system.

Expert system 225 and host expert system 275 use the processed sensordata to make recommendations and analyze the results. The expert systemis designed to utilize predictive analysis to predict the next actions,motions, stages of the user's activity, and to make recommendations.

Communication logic 230 in smart watch and host communication logic 280enable the close tying of the smart watch 210 and host device 260. Inone embodiment, communication logic 230 uses BLUETOOTH™ personal areanetwork (PAN). Other network communication methods may be used. BLE(BLUETOOTH LOW ENERGY) also known as BLUETOOTH SMART may be theconnection method. Other formats of network connection may be used. Inone embodiment, data is sent in packets, so that the connection time forthe transmission is minimized.

In one embodiment, the smart watch 210 may be physically coupled to thehost device, continuously or periodically. The extended band sharingsystem on the smart watch 235 and host 285, work together to shareprocessing and display. In one embodiment, the smart watch communicationis limited by the user interface elements 245 available on the smartwatch, such as a vibration motor and a limited number of subdials and/orLEDs, whereas in general, the host device 260 is a more fully featured,with a keyboard and screen.

User interface elements 245 on smart watch enable the user to interactwith the watch. In one embodiment, the band user interface elements mayinclude a button integrated into the watch crown, one or more subdialswith associated hands, a vibration motor, and optionally one or moreLEDs or a speaker or beeper. The user interface elements 245 on thesmart watch in general are more limited than the user interface elements292 in the host device 260. In one embodiment, the system is designed toprovide basic communication to the user via the smart watch 210, andprovide more details upon request via the host device 260.

Power control system 240 is used to minimize the power consumption bythe smart watch 210. The power control system 240 reduces the powerconsumption of the smart watch, by shutting off sensors that are notbeing utilized, reducing sensor sample rates based on the currentactivity of the user, reducing band power consumption when the band isnot being worn, and minimizing the use of the high power processing. Inone embodiment, the power control system is a smart system, activatingthe subset of sensors and processing power required on an as-neededbasis.

In one embodiment, data store on the band 258 may store sensor data fromsensors 215, prior to processing. Post-processing data may also bestored in data store 258. In one embodiment, data store 258 may be anon-volatile memory, such as a flash memory. Data store 299, on hostdevice 260 may be a non-volatile memory such as flash memory, or storagesuch as a disk drive. In one embodiment, the detailed long-term data isstored on a server (not shown), and sufficient data for display isstored on the host device 260. In one embodiment, the smart watch 210only stores the data not yet sent to the host device 260, and datauseful for the display, and calculations.

Pairing system 250 is used to initialize a connection between the smartwatch 210 and the host device 260. In one embodiment, the pairing mayuse an automatic pairing, triggered by shaking the devices together orperforming another activation mechanism. In one embodiment, themechanism described in U.S. Pat. No. 7,907,901 is used.

In one embodiment, multiple smart watches and/or other body-worn devices210 may be paired to a single host 260. This provides use flexibilityand fashion. For example, an attractive horological wrist watch that isworn during a workday may be suboptimal for exercise or sleep.Therefore, different bands may have different functionality.Additionally, different bands may have different appearances.Additionally, in one embodiment, a single body-worn device 210 may bepaired with multiple hosts 260. For example, a smart watch may be pairedwith the user's mobile phone, as well as the user's tablet computer,desktop, laptop, etc. Additionally a smart watch may be paired with aspecial purpose system.

In one embodiment, the system includes a help mode system 284, whichenables a connection to 911 or other emergency numbers, as appropriate.In one embodiment, help mode system provides an interface that enablesthe user to securely, quickly, and unobtrusively invoke an emergencyresponse from the smart watch 210, to trigger communication via hostdevice 260. In one embodiment, multiple help modes may be available,depending on the emergency. For example, a fire may be a different helpmode interface than a mugger or a medical emergency. In addition tobeing able to call 911 or the appropriate first responders, in onembodiment, help mode system 284 may also be set to contact a familymember, doctor, or other appropriate party.

Finder 252 enables the user to find the host device via the smart watch,and vice versa. In one embodiment, the proximity system can alert theuser when he or she leaves behind the smart watch 210, or the hostdevice 260. This can be useful especially when the user puts down thehost device 260, or takes off the smart watch 210 regularly. In thisway, the extended band formed by the band 210 and host device 260 canprovide an extended MACS (monitor, alert, control, share) system. Theextended band provides functionality which neither the band 210 nor thehost device 260 could provide alone. Additionally, by creating a trulylinked band 210 and host 260, rather than occasionally sharing data, theextended band can take advantage of the combined feature set of bothdevices.

As noted the host device 260 can provide a different set of sensors 265,data processing 270, expert system 275, etc. The host device 260 hasadditional user interface features, including a full screen andkeyboard. In one embodiment, the user can review his or her sleeppattern, activity pattern, and other health data on the host device 260via user interface elements 292. Host device 260 also has a serverconnection 282, in one embodiment, which enables the host device 260 toprovide data to the server. The server 282 in one embodiment stores userdata from multiple users, and provides calculations for predictivealgorithms, third party data, and updates. Though only a single serveris mentioned, it should be clear that the system may connect to multipleservers. For example, a first server may provide the application for thehost device 260, and updates to the application, while a second servermay be a data store for user data, and a third server may provide thirdparty data, and other information.

FIG. 3A is an overview flowchart of one embodiment of using the extendedband. FIG. 3A illustrates using a Bluetooth Low Energy (BLE, also knownas Bluetooth 4.0) connection. Of course, other embodiments may use otherwireless protocols. By preference, in one embodiment, low power wirelessprotocol is used. The process starts at block 310, when the smart watchis initially activated.

At block 320, the smart watch and the host devices are paired via thelow-power wireless protocol. In one embodiment, that protocol may be theBLE protocol. In one embodiment, pairing is done as described in FIG. 4below.

At block 330, a slow and low-power data connection is maintained betweenthe smart watch and the host device, to create the extended band. Theextended band is a combination of the sensors, processors, input andoutput mechanisms of the smart watch and the host device. Thecombination can provide better quality data, faster processing, and aricher output than either device alone.

At block 340, the process determines whether sensor data processing isdone by the host device, the smart watch, or a combination. In oneembodiment, if both the host device and the smart watch can doprocessing, the processing will be distributed as is most efficient. Inone embodiment, the decision may be made based on processor capability,available battery power, bandwidth cost, and sensor data volume. In oneembodiment, the host device has a more powerful processor but the smartwatch has more sensors. In one embodiment, pre-processed sensor data isshared, rather than raw data.

The process determines whether the processing is being done on the hostdevice, at block 340. If the processing is not done on the host device,at block 350, in one embodiment, sensor data is received by the smartwatch from the host device. If the processing is done on the hostdevice, at block 360, sensor data is sent to the host device by thesmart watch. In one embodiment, each device may do some preprocessing onits sensor data, before sharing it. Preprocessing data removesunnecessary data. For example, for a motion sensor, the accelerometeroutput is a change in acceleration at all times. The pre-processed datamay remove portions that contain no movement. In one embodiment, thepre-processed data, for an accelerometer, may provide an accelerationvector showing direction, strength, and length of movement, rather thanraw accelerometer data. In one embodiment, each device may process itssensor data separately.

At block 370, the data is processed to determine user recommendationsand outputs. In one embodiment, the outputs may be alarms, reminders,status indicators, status updates, etc. In one embodiment, feedback isoutput to the user at block 380. The feedback may additionally be sharedon social networks, or pushed to other users of the application, in oneembodiment. The process ends at block 390. In one embodiment, theconnection is maintained when the devices are both powered andavailable, and thus this process ends only when one of the two devicesis disconnected or turned off.

FIG. 3B is an overview flowchart of another embodiment of using theextended band. The process starts at block 315, when the smart watch andhost device are initially associated.

At block 325, the watch and host device are linked. In one embodiment,the pairing method described below with respect to FIG. 4 is used. Inone embodiment, the host device has the ability to “ping” when inpairing mode, and connect to any available smart watch. Other methods ofpairing or associating the devices may also be used.

At block 335, the process determines whether the sync is periodic. Aperiodic sync means that the data is shared between the watch and thehost device periodically. The period may be defined in various ways. Inone embodiment, the period may be defined by time, e.g. every fiveminutes, by data accumulation, e.g. after X amount of data is collected,by processor usage, e.g. when the watch processor is otherwise idle, byneed, e.g. when the watch is in need of additional sensor data orprocessing capability, or a combination of these or other perioddefinitions. In one embodiment, the host device may also initiate theperiodic synchronization. If the sync is periodic, at block 345, thesystem periodically exchanges data between the host device and the smartwatch. The process then continues to block 365.

If the sync is not periodic, the process continues to block 355. Atblock 355, data is exchanged between the smart watch and host device onrequest. The request may be a manual request from the user. The requestmay be an automatically generated request from the host device, or fromthe watch. For example, the host device may automatically request dataif the user activates the application and no recent data has beenreceived. For example, the watch may request data when the user placesthe watch into sleep state, and there is no alarm setting data availableon the watch, or the alarm setting data has not been validated recently.In one embodiment, the on-request data exchange may be a full dataexchange, or a limited data exchange as needed to service the user'sneeds. The process then continues to block 365.

At block 365, the data is processed, to determine user recommendationsand potential output. In one embodiment, the data processing includespredictive modeling of the user's expected activity/sleep pattern, andcomparison of actual sensor data against the predictive modeling. Thisenables the system to adjust the sensor and data processing frequency tomatch the expected actions, and to identify the actual actions morequickly and with less processing. The recommendations for the user mayrange from engaging in an activity, e.g. inactivity alarm, to coaching,e.g. providing guidance during an exercise session, to suggestions.

At block 385, feedback is provided to the user, if appropriate, via theextended band. As noted above, feedback via the smart watch may includedata displayed on a dial, or via LEDs, vibration, or alarm tones. Datadisplayed via the host device may be more detailed. In one embodiment,the feedback may be provided via alternative means, such as an email,SMS, or social media post.

The process ends at block 395. In one embodiment, the connection ismaintained when the devices are both powered and available, and thusthis process ends only when one of the two devices is disconnected orturned off.

FIG. 4 is a flowchart of one embodiment of pairing the mobile device andthe smart watch. This describes the initial pairing of a new watch to ahost device. In one embodiment, this flowchart corresponds to block 320of FIG. 3. The host device runs an application (app), which is used toprovide input/output for the extended band. The process starts at block410.

At block 420, the user launches the application, and chooses the optionto add a new smart watch. In one embodiment, this may be done from aconfiguration menu or the like in the application. In one embodiment,this may be done using a hardware button or similar mechanism.

At block 425, the application prompts the user to make sure the smartwatch is active and nearby, prior to pressing start. The start buttonmay be a soft button or a hard button. In another embodiment, the startbutton may be a gesture command or other initiation mechanism.

At block 430, the application searches for a smart watch that has areceived signal strength indicator (RSSI) greater than a threshold.

At block 440, the process determines whether a single watch is detected.If so, at block 445, the application prompts the user to complete thepairing. In one embodiment, this is done by performing a gesture commandto complete the pairing. This ensures that the watch whose signature wasdetected is the band being paired. The gesture command, in oneembodiment, is holding the host device and the watch together andperforming a motion. In another embodiment, button press or otherinteraction with the watch may be used instead to complete the pairing.In another embodiment, the watch ID (which may be the brand name, oranother identification) is displayed and the user can accept thepairing. In one embodiment, the user may need to accept the pairing onboth the watch and the host device, to ensure that an unrelated hostdevice can't be paired with a watch.

At block 450, the input is used to pair the host device and band. In oneembodiment, the process described in U.S. Pat. No. 7,907,901, assignedto the assignee of the present invention, may be used to perform thepairing. The user is informed of the pairing. The process then ends atblock 455.

If at block 440 the system did not detect a single watch, the processcontinued to block 460. At block 460, the process determines whether nowatches were detected. If no watches were detected at block 475 the useris informed that no watches were successfully detected, and the user isprompted to ensure that the watch to be paired is active and inproximity to the host device. The process then continues to block 470,enabling the user to reinitiate the pairing. If the user reinitiates thepairing, the process returns to block 430, to search for watches inproximity with an RSSI above a threshold. If the pairing is notreinitiated, the process ends.

If, at block 460 multiple watches and/or bands were found, in oneembodiment, the process continues to block 465. At block 465 the user iswarned that multiple devices were found in proximity, and prompted tomove, with the one watch to pair and the host device, or alternativelyto remove the other devices from the vicinity, or turn them off. Theprocess then continues to block 470, enabling the user to reinitiate thepairing. In another embodiment, the user may simultaneously pairmultiple watches or other devices with the host device. In that case,the process continues to block 445 when the one or more watches aredetected, and the user accepts the pairing with each device.

In this way, the system enables establishing the pairing between thehost device and the watch. Once a host device and a watch are paired,forming the extended band, whenever the two devices are in proximitythey can automatically establish a connection. Additionally, asdescribed above, the extended band utilizes the combined sensor set andprocessing power of the watch and the host device.

FIG. 5 is a flowchart of one embodiment of selecting a connection methodbetween the host device and the watch. In one embodiment, watches may beconnected to various host devices such as a smartphones, special purposemobile devices, tablet computers, mini tablets, laptop computers,desktop computers, or other devices. These various host devices may havedifferent capabilities, in terms of types of wireless connectivity. Thetypes of wireless connectivity may include various types of wirelesspersonal area networks (WPAN), local area networks (LAN), 802.11-typenetworks, and other types of connections.

At block 515, the types of connections available between the watch andhost devices are identified. The types of connections include allconnection formats that are supported by both the host device and thewatch.

At block 520, the lowest power connection that can support the dataexchange between the watch and host device is selected. Because thewatch is designed to monitor motion, sleep, and ergonomics, it isdesigned to be worn continuously. Therefore, long battery life isstrongly preferred, and minimizing power consumption is an importantgoal.

At block 525, a connection pattern that is the lowest consumption isselected. Depending on the type of connection, the lowest consumptionpattern may be a continuous connection sending small amounts of data(Bluetooth 4.0) or periodic connections to send high bandwidth bursts ofdata. In one embodiment, based on the connection method selected, thelowest power connection pattern is selected.

At block 530, the process determines whether the selected connectionpattern is continuous. As noted above, for some connection formats, acontinuous low power connection is preferred. If so, at block 540, thesystem is set up to use a continuous connection, at block 540. In oneembodiment, the continuous connection exchanges data in a low bandwidthformat regularly. If not, at block 535 the system sets up timing forperiodic connections, or sets up a pattern of establishing connectionsas needed. The process then ends.

FIG. 6 is a flowchart of one embodiment of handling lost connections inthe extended band. In one embodiment, the extended band assumes thatthat connection between the watch and the host device is on-going,either continuously or on a periodic basis. When the systems cannotconnect, in one embodiment, the following process is used. The processstarts at block 610. In one embodiment, this process is continuously orperiodically validating the connection.

At block 615, the process determines whether the connection was dropped.A dropped connection occurs if an attempt to share data between thewatch and the host device fails. In one embodiment, at least a pluralityof attempts must fail, to declare a connection dropped. In oneembodiment, if three attempts fail, the connection is deemed dropped.

If the connection has not dropped, at block 650 the combination of watchand host device is used to acquire sensor data, process it, andcommunicate with the user. Additionally the extended band may share datawith third parties including social networks, as well as present data tothe user, in one embodiment including from third parties includingsocial networks. The process continues back to block 615, to continueutilizing the extended band and monitoring for a dropped connection.

If the connection was dropped, at block 620 the user is alerted via thewatch and/or host device, in one embodiment. The alert may be useful toindicate that the watch or host device was left behind accidentally, hasbeen turned off, or has developed a problem. In one embodiment, thealert on the watch may be a vibration or light, while the host devicemay use an alarm tone and a display on its screen. Other methods ofalerting the user may be used. In one embodiment, a text or MMS messagemay be generated to alert the user.

At block 625 the watch wireless connection is put to sleep. As notedabove, the watch power use should be minimized. Wireless connectivity isone of the significant battery drains, and especially unsuccessfulattempts to connect wirelessly uses a lot of signal strength and thusbattery. Therefore, temporarily placing the watch's wireless connectionin a sleep state is a way of preserving battery power.

At block 627, the other processes of the watch are continued, at areduced level. In one embodiment, if the watch cannot process some ofthe sensor data, it stores and queues the data to be sent to the hostdevice. From the user's perspective, in one embodiment, the watchfunctionality does not significantly change, unless the watch cannotsupport the required processing. In that case, the system attempts tocontinue functioning with the reduced processing power, prioritizinguser-relevant actions. For example, if the user is sleeping and awaitingan alarm, the watch would continue to monitor sleep and ensure that thealarm was not missed. Other processes may be queued for laterprocessing. The watch also queues other communications that wouldnormally take place with the host device, e.g. user status updates andprocessed sensor data.

At block 630, the process determines whether a qualifying event hastaken place. A qualifying event may include the user pressing a buttonon the band, ending a sleep or timed steps recording, the watchdetecting that it is time to wake-up the user (smart sleep alarm), etc.In one embodiment, a qualifying event is any event that should lead tocommunication between the host device and the watch. If a qualifyingevent is detected, at block 640 the watch wireless connection is woken,and the watch attempts to connect to the host device again. At block645, the process determines whether the connection was reestablished. Ifnot, the process continues to block 625, and puts the wirelessconnection back to sleep. Of course, the watch would also perform theactions triggered by the qualifying event. If the connection issuccessfully reestablished, the watch sends the data previously queuedto the host device, and the process returns to block 615 to continueinteracting with the host device and monitor the status of theconnection.

If no qualifying event took place, at block 630, at block 635 theprocess determines if a timer has triggered. If the time set by thetimer has not passed, the process returns to block 627, to continuereduced service, and determine whether a qualifying event has beendetected. If the timer has been triggered, at block 640 the watchwireless is woken, and a connection is attempted.

In this way, the almost continuous connection between the watch and thehost device is maintained, while optimizing for reduced powerconsumption by the watch and user-relevant processing when processing islimited to the watch. Although this figure shows the dropped connectionfrom the perspective of the watch, one of skill in the art wouldunderstand that the host device can use a similar process. When thesensor data, and other information from the watch is not available, thehost device continues to process what data it has available, andattempts to keep the user experience consistent. In one embodiment, ifthe system is being used for sleep monitoring, the host device maychange to a user-modified sleep pattern, and still wake the user using asmart alarm. This is designed to ensure that if the watch runs out ofpower, or crashes, or otherwise becomes inactive, the user still has apositive experience with the system.

FIG. 7 is a flowchart of one embodiment of using the extended band. Theprocess starts at block 710. At block 715, the process determineswhether the watch is above a motion threshold. This determinationattempts to identify whether the watch is being worn, or not. Even whennot moving a human body exhibits certain motions, such as tremors and arhythmic movement caused by the heart beating. The motion threshold isset, in one embodiment, to be able to use these involuntary motions todetermine that the watch is in use.

If the watch is below the motion threshold, at block 720 the processdetermines whether the watch has been inactive for a period of time. Ifso, at block 725, the sensors in the watch are powered off, or placed ona low testing frequency. The process then ends at block 730. In oneembodiment, the watch sets a timer, and periodically checks if there ismovement above a threshold. In another embodiment, at least one sensoris maintained at a low rate, to continue monitoring. The sensor may bethe temperature sensor, accelerometer, or other low power sensor that iscapable of detecting either motion or temperature or another identifierthat would indicate that the watch is being worn. In another embodiment,the user manually activates the sensors in the watch after they arepowered off. In one embodiment, a dial may set the watch to a settingindicating that the sensors are off.

If the watch has not been inactive for a period, the process returns toblock 715, to continue monitoring whether the watch motion level isabove the threshold.

If the watch motion is above the threshold, as determined at block 715,the process continues to block 740. At block 740, the process determineswhether host device finder was initiated on the watch. In oneembodiment, when the user is wearing the watch and cannot find his orher host device, which is a mobile device, he or she may activate thisfeature. If it was activated, at block 745 a message is sent to triggeran action on the host device. In one embodiment, the message is sentthrough the application that may be able to override a silent setting.This enables the user to locate the host device, if the host device hasany power. In one embodiment, the output is played repeatedly until theuser indicates that the host device has been found. In one embodiment,if the watch and host device are not in close enough proximity to usethe personal area network such as BLUETOOTH, another network protocolmay be used for this message. The process then returns to block 715.

If the host device finder is not activated, the process determineswhether the watch device finder on the host device is activated, atblock 750. If so, at block 755, a message to use the watch output issent from the host device to the watch. The output may be a sound, avibration, a flashing light, or a combination of those or any otherforms of output that the watch can utilize. In one embodiment, theoutput is played repeatedly until the user indicates that the watch isfound. In one embodiment, if the watch and host device are not in closeenough proximity to use the personal area network such as BLUETOOTH,another network protocol may be used for this message. In oneembodiment, if the host device has the capability to determine thelocation of the watch, the system may also provide an indication of thelocation or approximate direction of the band. The process then returnsto block 715.

If the watch finder was not initiated, at block 760, the processdetermines whether a help mode is initiated. The help mode may beinitiated by pressing and holding a button, or another indication on thewatch. In one embodiment, this indication is designed to not beaccidentally triggered, and easy enough to enable someone who is hurt toperform the indication.

In one embodiment, the user may utilize the watch to initiate a helpmode. The help mode connects the user to an emergency number, such as911 or a pre-programmed third party such as a doctor or monitoringservice, using a combination of the watch and the host device. Thiswould enable a user who is unable to reach or dial a telephone to callfor help.

If the help mode is initiated, at block 765, the system uses theextended band to connect to the emergency line. In one embodiment, thecombination of the host device and the watch enables a user to talk tothe emergency number responder (such as a dispatcher) without having todial and hold a telephone. In one embodiment, there may be multipletypes of help modes that may be triggered. For example, there may be a“medical emergency” trigger, a “non-medical emergency” trigger, and a“dangerous situation” trigger. In one embodiment, the user may defineone or more triggers, and one or more destinations. In one embodiment,the default help mode initiation is to contact 911 or the equivalentlocal emergency service.

In one embodiment, help mode may be initiated automatically, e.g.without a user triggering it, in some circumstances. For example, in oneembodiment, if the watch sensors detect that the user is having amedical emergency, help mode may be initiated. For example, if the watchcan monitor heart rate automatically, a heart rate in the danger zone(e.g. heart arrhythmia or heart racing without a corresponding movementtrigger) may automatically trigger the help mode. In one embodiment, theuser is provided with the opportunity to override the help mode trigger,if it is automatically initiated. In one embodiment, the ability toterminate the help mode is also provided when it is manually triggered,enabling the user to override it. The process then returns to block 715to continue monitoring.

If no help mode was initiated, the process at block 770 determineswhether the system has received data from other users. In oneembodiment, the user may set up one or more “friends” with whom the userwishes to share data, and whose data the user wishes to see. If one ofthose friends has sent data, at block 775 the data is received andshared with the user. In one embodiment, the system includes a page thatdisplays the user's own status and the status of friends. The datareceived may include social media posts, such as posts on FACEBOOK®, orTWITTER® or another social media platform. The data received may includedata directly shared between instances of the application, e.g. eachuser may set up to share certain milestones achieved, such as how muchand how well the user slept, how much aerobic activity the user did, howmany steps the user took, etc. In one embodiment, the received data is acombination of these types of data. In one embodiment, the user may bealerted to certain social media data, based on user-set preferences. Theprocess then returns to block 715 to continue monitoring.

If no data is received, at block 780, the system provides normal userstatus to the user throughout the day. The user interface on the watchis updated throughout the day, as is the user interface available via anapplication on the host device so that it is up-to-date with the user'slatest activity and/or sleep data. It is designed so that the user canglance at the watch and see how he or she is doing today. In oneembodiment, by incorporating the shared data received from others, theuser can also see one the host device how he or she is doing relative topersonal activity/sleep goals and relative to other people/friends intheir social network.

In one embodiment, the watch also provides some of this feedbackthroughout the day. In one embodiment, the watch has subdial whichprovides progress information, using a dial and hand, which allows forfeedback/status updates throughout the day. In one embodiment, theuser's current status may be reflected by an LED or other illustratingshowing a relative status (e.g. green when the user has met his or hergoals, shading into yellow as they slip, and red when the user is farfrom his or her set goals). Alternatively, the user's relative standingamong his or her friends may be indicated via display on the watch. Forexample, there may be a dial indicating user status, with the dialpointing to a gold, silver, bronze, or other level, depending on theuser's relative placement. In one embodiment, LEDs with various colorsmay be used. This enables an at-a-glance comparison between friends. Inone embodiment, a competition logic, described for example in U.S.patent application Ser. No. 11/740,884, assigned to the assignee of thiscase, may be used to enable competition between unevenly matched users.

In one embodiment, in addition to providing data to the user, theprocess also enables the user to selectively share the user's statuswith friends. As noted above, the application may share certainachievements and status. In one embodiment, the user sets up whatinformation is shared with whom, and once the preferences are set, theextended band automatically shares data. In one embodiment, the user mayalso manually share data, or block data from being shared. The processthen returns to block 715 to continue monitoring.

In this way, the extended band, utilizing the watch and the paired hostdevice provide services to the user. Additional services may beprovided, with sensor data, sensor data processing, data sharing, andnotifications utilizing the watch, the host device, or both devices. Byproviding an extended band that is linked consistently with the hostdevice, the user has the advantages of both form factors, and thedisadvantages of neither.

FIG. 8 is a flowchart of one embodiment of optimizing the sharing orprocessing and display on the extended band. The process starts at block810. In one embodiment, this process is continuous when the extendedband is in use.

At block 815, the process determines whether there is user output to beprovided. The system provides alerts, alarms, and other types ofnotifications to the user. In one embodiment, this does not includeupdates to the user's information presented on the watch or host device,as discussed with respect to FIG. 7.

If there is user output to be provided, the system at block 820identifies the optimal combination of outputs based on the type ofconnection between the host and band, power levels of the host and band,and host and band capabilities. In one embodiment, the systempreferentially outputs user alerts through the watch, and more detaileddata through the host device, since the host device provides a richerexperience. In one embodiment, the relative location of the host deviceand watch may also be taken into account, e.g. if the user is wearingthe watch but the host device is not nearby, the watch may be a betteroutput mechanism. In one embodiment, the distance between the host andwatch may be determined based on connection latency. In one embodiment,if one of the devices has low power, the system preferentially uses theother device in the extended band to provide feedback to the user. FIG.9 illustrates some exemplary methods of providing output to the user. Inone embodiment, the watch includes one or more subdials, and a vibrationengine, to provide information to the user. In one embodiment, the handson the subdials are moved via micro-motors. Any of the exemplaryinterface methods discussed in FIG. 9 may be altered, of course, withoutdeviating from the present invention. Once the optimal combination ofthe outputs is determined, at block 825 the output is provided to theuser. The process then returns to block 815 to continue monitoring.

If there is no output to be provided, the process determines whetherthere is data to be processed. The data to be processed may includesensor data such as motion data, heart rate data, or other types ofdata. The data to be processed may also include third party data. In oneembodiment, data processing includes not only using raw sensor data todetermine the user's activities, sleep phase, ergonomics, etc., but alsoproviding trend analysis and other processing. If there is data to beprocessed, at block 835 the process identifies the ideal combination ofthe watch and host device, and optionally a remote system such as aserver, to process the data. In one embodiment, this too may be based onthe capabilities, power levels, and data sets available to the devices.The process at block 840 then determines whether the data needs to bepassed from its current source for processing. If not, the processingtakes place and the process returns to block 815 to continue monitoring.

If at block 840 the process determines that the data needs to be passed,at block 845 the data is passed from the watch to the hostdevice/server, or from the host device to the watch/server, or in someother configuration, as determined. The data is then processed. In oneembodiment, if the other device will use the data, in one embodiment theprocessed data, and/or the conclusion that results from the processing,is passed back at block 850. In another embodiment, the result of theprocessing is passed back. In one embodiment, a relevant output orchange in settings or state based on the data is passed back. In anotherembodiment, no data is returned. The process then returns to block 815to continue monitoring.

If there is no data to be processed, at block 855 the process determineswhether there is sensor data to be shared. If so, at block 860 thesensor data is received. The sensor data may be received by the watchfrom the host device, or by the host device from the watch. The processthen returns to block 815 to continue monitoring.

If there is no sensor data to be shared, the process continues to block865. At block 865, the process determines whether the watch or hostdevice is low on power. If a watch or host device is low on power, inone embodiment, the system attempts to reduce the likelihood that itwill run out of power entirely, by reducing the demands made by theextended band on the low-battery device.

If a device is low on power, at block 875 the processing and output isshifted to the other device. At block 880, the inessential elements ofthe device are turned off. For example, if the watch is low on power, inone embodiment, all sensors except the motion sensor may be turned off.In one embodiment, if the host device has an available motion sensor andis being carried, the motion sensor may also be turned off. In normaluse, when power levels are not an issue, the host device and the watchmay both monitor user motions, to provide amore detailed picture of theuser's activities. However, when a power issue comes up, the elementsnot absolutely necessary may be turned off, to extended battery power.If there is no power issue, the process continues directly to block 815.In one embodiment, the system may minimize power consumption even whenthere is not a low power issue. In that case, in one embodiment, onlyone carried device would monitor movement and other physiological data,and only one device outputs information to the user. This is lessaccurate than having two sets of data, but is more power efficient. Inone embodiment, the trade-off level may be set by the user. The processthen returns to block 815, to continue monitoring the user.

FIG. 10 is a flowchart of one embodiment of showing data on the smartwatch using the horological display. The process starts at block 1010.In one embodiment, this process is active whenever the smart watch isactive.

At block 1015, the system receives motion and other available data fromsensors in the watch. In one embodiment, the sensors may includetemperature, acceleration/gyroscope or other motion sensors, magneticsensors, barometers, heart rate sensors, etc. In one embodiment, datamay also be received from sensors in the host device, or externalsensors.

At block 1020, the data is processed using predictive logic. Predictivelogic utilizes the existing information about the user and the patternsof behavior to predict future behavior. This allows the system tocompare the actual data to the predicted data, and confirm or disprovethe expected behavior. This enables analysis of behavior based on lessdata, and with less processing.

At block 1025, the process determines whether the watch is in sleepstate. If so, at block 1030, the sleep phase is determined. The sleepphase is predicted based on the past sleep states, the time, and thesleep cycles of the user. The sleep phase is verified using the sensordata. Once the actual sleep state is identified, the data is added tothe data store. At block 1035, in one embodiment, the percentage ofsleep, compared to the sleep goal is incremented. The hands are moved onthe dial, to visually represent the percentage sleep achieved, comparedto the set sleep goal. In one embodiment, the display may represent notonly an overall sleep goal, but also a sleep goal by sleep phase (e.g.hours in each sleep phase, N1, N2, N3, and REM sleep, or deep sleep &REM sleep.) In one embodiment, this type of additional data may also berepresented on the watch. The process then returns to block 1015, tocontinue monitoring the user.

If the watch is not in sleep state, the process continues to block 1040.At block 1040, step data is calculated for the user and added to thedata store. Again, in one embodiment, the predictive logic makes a baseassumption, for example, if the user is walking and not at a known endlocation, the user will keep walking. The sensor data is used tovalidate the assumption. The result is added to the data store.

At block 1045, the number of steps or percentage of steps to the stepgoal is incremented, and the hands of the watch are moved to representthe current results. In one embodiment, in addition to measuring a stepgoal, the system may alternatively or additional measure vigorousexercise, overall activity, and other measurements.

At block 1050, the process determines whether the user has been inactivefor a set period. In one embodiment, the user may configure the watch toalert him or her after a certain period of inactivity. For example, thewatch may buzz or chime after the user has been inactive for at least 30minutes. This period, and the presence of this alert, may be configuredby the user, on the host device.

If the user has been inactive, at block 1055, the user is alerted tomove. In one embodiment, the alert may be a vibration or tone on thewatch, or a more detailed alert on the host device. In one embodiment,the user may be prompted, on the host device, to stretch or otherwisebecome active for a short period. It is unhealthy to be sitting stillfor extended periods, and by sending such alerts, the user's overallwellbeing is improved. The process then returns to block 1015, tocontinue monitoring the user. If the user has not been inactive, theprocess returns to block 1015 directly, to continue monitoring the user.

FIG. 11 is a flowchart of one embodiment of resetting the hands on thewatch, in accordance with the present system. The process starts atblock 1110. This process in one embodiment is started when the smartwatch is initially configured.

At block 1120, the hands of the smart watch are set to the initialstarting position. This is needed for the system to be properlyinitialized. This may be done at the time of assembly or initialization.

At block 1130, the micromotors are used to move the hands in thehorological device, one or more subdials. The subdials may presentinformation about the user's activity, sleep, or other aspect monitoredby the smart watch. Dials may include hands, pointing to a number orsymbol, or a window displaying a number or symbol, such as a datewindow. The horological dial shows the current time, and optionally day.Other aspects that may be displayed via subdials may be a stateindicator, indicating smart watch state (e.g. awake, sleeping, andactive), the percent or total steps taken or sleep achieved, etc.

At block 1140, a tracker is adjusted, based on the motion and themovement. The tracker tracks the movements of the hands, whether thosemovements are caused by the micromotors (e.g. actual changes) or byjarring or other issues.

At block 1150, the process determines whether another display isrequested. In one embodiment, the hands may have multiple outputfunctions, for example time and health status, or date and step goalpercentage, etc. If another display is requested, at block 1160 theappropriate dial(s) are adjusted for the requested data. The tracker, inone embodiment, continues tracking all changes to the display. Theprocess then continues o block 1170.

At block 1170, the process determines whether a reset of the hands isrequested or needed. A reset is requested when the user wants to adjustthe hands, either to reset from a different display, or because the userhas noticed a discrepancy between the display and the actual time. Thesystem may automatically detect that a reset is needed, at block 1170,when the location of the hands, based on the tracker data, does notcorrespond to the actual location of the hands.

At block 1180, the hands are aligned automatically based on the trackerdata. As noted, the tracker data tracks each movement of the hands. Thisenables the system to recreate the accurate expected location of thehands, even if the system has been misaligned because it was dropped orexperienced some other issue.

At block 1190, once the hands are aligned, the hands are automaticallymoved to the current time location, based on data from the host device.The host device may obtain clock information via a cellular network,global positioning system, wireless network, Internet connection orthrough some other means. This data is used to reset the hands of thesmart watch. The process then returns to block 1130, to continuecontrolling the hands of the device using micromotors.

In one embodiment, the tracker uses markings on the dial or hand, totrack movements. By using such a tracker system, enabled by theprocessor and other elements present in a smart watch, the frustratingresetting of a clock display is avoided.

One of ordinary skill in the art will recognize that the processesdescribed in the above flowcharts are conceptual representations of theoperations used. The specific operations of the processes may not beperformed in the order shown and described. For example and in oneembodiment, the process is interrupt driven, rather than sequentiallytesting for various occurrences. In one embodiment, data is received orprocessed in a different order. The specific operations may not beperformed in one continuous series of operations, and different specificoperations may be performed in different embodiments. Additionaloperations may be performed, or some operations may be skipped.Furthermore, the processes could be implemented using severalsub-processes, or as part of a larger macro process. For instance, insome embodiments, the processes shown in these flowcharts are performedby one or more software applications that execute on one or morecomputing devices.

FIG. 12 is a block diagram of one embodiment of a computer system thatmay be part of the present invention. FIG. 12 is a block diagram of aparticular machine that may be used with the present invention. It willbe apparent to those of ordinary skill in the art, however that otheralternative systems of various system architectures may also be used.

The data processing system illustrated in FIG. 12 includes a bus orother internal communication means 1240 for communicating information,and a processing unit 1210 coupled to the bus 1240 for processinginformation. The processing unit 1210 may be a central processing unit(CPU), a digital signal processor (DSP), or another type of processingunit 1210.

The system further includes, in one embodiment, a random access memory(RAM) or other volatile storage device 1220 (referred to as memory),coupled to bus 1240 for storing information and instructions to beexecuted by processor 1210. Main memory 1220 may also be used forstoring temporary variables or other intermediate information duringexecution of instructions by processing unit 1210.

The system also comprises in one embodiment a read only memory (ROM)1250 and/or static storage device 1250 coupled to bus 1240 for storingstatic information and instructions for processor 1210. In oneembodiment the system also includes a data storage device 1230 such as amagnetic disk or optical disk and its corresponding disk drive, or Flashmemory or other storage which is capable of storing data when no poweris supplied to the system. Data storage device 1230 in one embodiment iscoupled to bus 1240 for storing information and instructions.

The system may further be coupled to an output device 1270, such as acathode ray tube (CRT) or a liquid crystal display (LCD) coupled to bus1240 through bus 1260 for outputting information. The output device 1270may be a visual output device, an audio output device, and/or tactileoutput device (e.g. vibrations, etc.)

An input device 1275 may be coupled to the bus 1260. The input device1275 may be an alphanumeric input device, such as a keyboard includingalphanumeric and other keys, for enabling a user to communicateinformation and command selections to processing unit 1210. Anadditional user input device 1280 may further be included. One such userinput device 1280 is cursor control device 1280, such as a mouse, atrackball, stylus, cursor direction keys, or touch screen, may becoupled to bus 1240 through bus 1260 for communicating directioninformation and command selections to processing unit 1210, and forcontrolling movement on display device 1270.

Another device, which may optionally be coupled to computer system 1200,is a network device 1285 for accessing other nodes of a distributedsystem via a network. The communication device 1285 may include any of anumber of commercially available networking peripheral devices such asthose used for coupling to an Ethernet, token ring, Internet, or widearea network, personal area network, wireless network or other method ofaccessing other devices. The communication device 1285 may further be anull-modem connection, or any other mechanism that provides connectivitybetween the computer system 1200 and the outside world.

Note that any or all of the components of this system illustrated inFIG. 12 and associated hardware may be used in various embodiments ofthe present invention.

In one embodiment, the band may include a subset of these elements, suchas a processor, flash memory, input/output mechanism, and communicationsmechanism. The host device may include a subset of superset of theseelements, but at least a processing device and a communication device.

It will be appreciated by those of ordinary skill in the art that theparticular machine that embodies the present invention may be configuredin various ways according to the particular implementation. The controllogic or software implementing the present invention can be stored inmain memory 1220, mass storage device 1230, or other storage mediumlocally or remotely accessible to processor 1210.

It will be apparent to those of ordinary skill in the art that thesystem, method, and process described herein can be implemented assoftware stored in main memory 1220 or read only memory 1250 andexecuted by processor 1210. This control logic or software may also beresident on an article of manufacture comprising a computer readablemedium having computer readable program code embodied therein and beingreadable by the mass storage device 1230 and for causing the processor1210 to operate in accordance with the methods and teachings herein.

The present invention may also be embodied in a handheld or portabledevice containing a subset of the computer hardware components describedabove. For example, the handheld device may be configured to containonly the bus 1240, the processor 1210, and memory 1250 and/or 1220.

The handheld device may be configured to include a set of buttons orinput signaling components with which a user may select from a set ofavailable options. These could be considered input device #1 1275 orinput device #2 1280. The handheld device may also be configured toinclude an output device 1270 such as a liquid crystal display (LCD) ordisplay element matrix for displaying information to a user of thehandheld device. Conventional methods may be used to implement such ahandheld device. The implementation of the present invention for such adevice would be apparent to one of ordinary skill in the art given thedisclosure of the present invention as provided herein.

The present invention may also be embodied in a special purposeappliance including a subset of the computer hardware componentsdescribed above, such as a kiosk or a vehicle. For example, theappliance may include a processing unit 1210, a data storage device1230, a bus 1240, and memory 1220, and no input/output mechanisms, oronly rudimentary communications mechanisms, such as a small touch-screenthat permits the user to communicate in a basic manner with the device.In general, the more special-purpose the device is, the fewer of theelements need be present for the device to function. In some devices,communications with the user may be through a touch-based screen, orsimilar mechanism. In one embodiment, the device may not provide anydirect input/output signals, but may be configured and accessed througha website or other network-based connection through network device 1285.

It will be appreciated by those of ordinary skill in the art that anyconfiguration of the particular machine implemented as the computersystem may be used according to the particular implementation. Thecontrol logic or software implementing the present invention can bestored on any machine-readable medium locally or remotely accessible toprocessor 1210. A machine-readable medium includes any mechanism forstoring information in a form readable by a machine (e.g. a computer).For example, a machine readable medium includes read-only memory (ROM),random access memory (RAM), magnetic disk storage media, optical storagemedia, flash memory devices, or other storage media which may be usedfor temporary or permanent data storage. In one embodiment, the controllogic may be implemented as transmittable data, such as electrical,optical, acoustical or other forms of propagated signals (e.g. carrierwaves, infrared signals, digital signals, etc.).

In one embodiment, the host device is computer system with the expertsystem and analysis performed by a processor, DSP, or similarprocessing-capable device. In one embodiment, the host and/or band mayinclude multiple processors, such as a low power processor and a highpower processor. In one embodiment, the sensors may be separatelypowered as well.

In the foregoing specification, the invention has been described withreference to specific exemplary embodiments thereof. It will, however,be evident that various modifications and changes may be made theretowithout departing from the broader spirit and scope of the invention asset forth in the appended claims. The specification and drawings are,accordingly, to be regarded in an illustrative rather than a restrictivesense.

We claim:
 1. A smart watch comprising: at least one sensor within thesmart watch to track a user's movements using a motion sensor; aprocessor within the smart watch to process data from the at least onesensor, and determine information about the user, based on themovements; a watch case, including a watch face having at least one dialand a subdial, the watch case including the sensor and the processor,the subdial to display information about the user, based on themovements, wherein the information comprises one of: activityinformation and sleep information.
 2. The smart watch of claim 1,wherein the processor and sensor are in the watch case.
 3. The smartwatch of claim 1, further comprising: a communication system to pair thesmart watch to a host device, the host device and the smart watch bothproviding information to the user.
 4. The smart watch of claim 3,wherein the pairing of the smart watch and the host device comprises oneof: a continuous low power connection, a periodic connection, and anon-demand connection, to share data.
 5. The smart watch of claim 3,wherein the host device provides a user interface, enabling a user toset preferences.
 6. The smart watch of claim 1, wherein the subdialdisplays one or more of: a percentage of a step goal currently reached,a percentage of a sleep goal currently reached, a number of steps taken,a number of hours slept, a watch state selected from among awake,asleep, and active.
 7. The smart watch of claim 1, further comprising: acommunication system to share sensor data between the smart watch and ahost device; and sensor processing system to analyze the sensor data todetermine the user's state and identify user state changes.
 8. The smartwatch of claim 1, further comprising: a tracker to track movement ofhands on the dial, indicating time, the tracker used to enable automaticrealignment of the hands by tracking each motion of the hands andcomparing the motion against an actual change in time based on data froma host device.
 9. A smart watch system comprising: a motion sensorwithin a smart watch to track motion data; a processor within the smartwatch to process data from the at least one sensor, and determineactivity and sleep information, based on the motion data; a watch case,including a watch face having at least one dial and a subdial, the watchcase including the motion sensor and the processor, the subdial todisplay the activity information or the sleep information; and a trackerto track movement of hands on the dial indicating time, the tracker usedto enable automatic realignment of the hands by tracking each motion ofthe hands and comparing the motion against an actual change in timebased on data from a host device.
 10. The smart watch system of claim 9,further comprising: a communication system to pair the smart watch tothe host device, the host device and the smart watch both displayinginformation to the user.
 11. The smart watch system of claim 10, whereinthe pairing of the smart watch and the host device comprises one of: acontinuous low power connection, a periodic connection, and an on-demandconnection, to share data.
 12. The smart watch system of claim 10,wherein the host device provides a user interface, enabling a user toset preferences for the smart watch.
 13. The smart watch system of claim9, wherein the subdial displays either a percentage of a step goalcurrently reached or a percentage of a sleep goal currently reached. 14.The smart watch system of claim 9, further comprising: a communicationsystem to share sensor data between the smart watch and a host device;and sensor processing system to analyze the sensor data to determine theuser's state and identify user state changes.
 15. A system comprising: asmart watch including a watch case comprising: a motion sensor to trackmotion data; a processor to process data from the motion sensor, anddetermine activity and sleep information, based on the motion data; awatch face having at least one dial and a subdial, the watch caseincluding the motion sensor and the processor, the subdial to displaythe activity information or the sleep information; and a host devicepaired with the smart watch, the host device comprising: a host deviceprocessor; a communication system to communicate with the smart watch;and a digital display to provide a more detailed display of the activityinformation and the sleep information, based on the motion data.
 16. Thesystem of claim 15, further comprising: a tracker to track movement ofhands on the dial indicating time, the tracker used to enable automaticrealignment of the hands by tracking each motion of the hands andcomparing the motion against an actual change in time based on data fromthe host device.
 17. The system of claim 15, wherein the pairing of thesmart watch and the host device comprises one of: a continuous low powerconnection, a periodic connection, and an on-demand connection, to sharedata.
 18. The system of claim 15, wherein the host device provides auser interface, enabling a user to set preferences for the smart watch.19. The system of claim 15, wherein the subdial displays either apercentage of a step goal currently reached or a percentage of a sleepgoal currently reached.
 20. The system of claim 15, wherein the hostdevice further comprises: an additional sensor; the host deviceprocessor to process data from the additional sensor and integrate itwith data from the motion sensor.